Contextual generation of ephemeral networks

ABSTRACT

A method, system, and computer program product for contextual generation of an ephemeral network are provided. The method detects an initiating event for network generation associated with a user of a first computing device. The method determines a duration of the initiating event. A set of network members is determined based on the initiating event and the duration. The method establishes an ephemeral network, connecting at least a portion of computing devices associated with the set of network members. The ephemeral network is terminated in response to detecting a completion event. In response to terminating the ephemeral network, member information for the set of network members is removed from the portion of the computing devices.

BACKGROUND

Many vehicle manufacturers incorporate infotainment systems intocommercially available vehicles. These infotainment systems providevarying types of information, interaction, and connectivity to driversand passengers of vehicles. Infotainment systems may present informationsuch as maps, navigation information, vehicle camera feeds, messaging,internet browsing, music playback, and other types of audio/visualinformation. Infotainment systems often enable interaction withpresented information through touchscreens, manual controls, wired andwireless connections to mobile computing devices, and other input/outputoptions. Infotainment systems may access and store information from adriver or passenger device based on connection methods and applicationsused by or presented by the infotainment system. Some infotainmentsystems access and store user information such as contact information,addresses, navigation routes, locations (e.g., work, home, orfavorites), accessed network resources, and even messaging data. Thisuser data may be retained by infotainment systems, intentionally orinadvertently. Users may accept such storage of personal data on apersonally owned vehicle. However, storage or retention of such data intemporarily accessed vehicles, such as rental and rideshare vehicles,presents risks to owners of such personal information.

SUMMARY

According to an embodiment described herein, a computer-implementedmethod for contextual generation of an ephemeral network is provided.The method detects an initiating event for network generation. Theinitiating event is associated with a user of a first computing device.The method determines a duration of the initiating event. The methodthen determines a set of network members based on the initiating eventand the duration. The set of network members are associated with a setof computing devices. The method establishes an ephemeral networkconnecting the computing devices associated with the set of networkmembers. The method terminates the ephemeral network in response todetecting a completion event and removes member information for the setof network members in response to terminating the ephemeral network.

According to an embodiment described herein, a system for contextualgeneration of an ephemeral network is provided. The system includes oneor more processors and a computer-readable storage medium, coupled tothe one or more processors, storing program instructions that, whenexecuted by the one or more processors, cause the one or more processorsto perform operations. The operations include detecting an initiatingevent for network generation. The initiating event is associated with auser of a first computing device. The system determines a duration ofthe initiating event. The system then determines a set of networkmembers based on the initiating event and the duration. The set ofnetwork members are associated with a set of computing devices. Thesystem establishes an ephemeral network connecting the computing devicesassociated with the set of network members. The system terminates theephemeral network in response to detecting a completion event andremoves member information for the set of network members in response toterminating the ephemeral network.

According to an embodiment described herein a computer program productfor contextual generation of an ephemeral network is provided. Thecomputer program product includes a computer readable storage mediumhaving program instructions embodied therewith, the program instructionsbeing executable by one or more processors to cause the one or moreprocessors to perform operations including detecting an initiating eventfor network generation. The initiating event is associated with a userof a first computing device. The computer program product determines aduration of the initiating event. The computer program product thendetermines a set of network members based on the initiating event andthe duration. The set of network members are associated with a set ofcomputing devices. The computer program product establishes an ephemeralnetwork connecting the computing devices associated with the set ofnetwork members. The computer program product terminates the ephemeralnetwork in response to detecting a completion event and removes memberinformation for the set of network members in response to terminatingthe ephemeral network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram of a computing environment forimplementing concepts and computer-based methods, according to at leastone embodiment.

FIG. 2 depicts a flow diagram of a computer-implemented method forcontextual generation of an ephemeral network, according to at least oneembodiment.

FIG. 3 depicts a flow diagram of a computer-implemented method forcontextual generation of an ephemeral network, according to at least oneembodiment.

FIG. 4 depicts a block diagram of a computing system for contextualgeneration of an ephemeral network, according to at least oneembodiment.

FIG. 5 is a schematic diagram of a cloud computing environment in whichconcepts of the present disclosure may be implemented, in accordancewith an embodiment of the present disclosure.

FIG. 6 is a diagram of model layers of a cloud computing environment inwhich concepts of the present disclosure may be implemented, inaccordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION

The present disclosure relates generally to methods for establishingephemeral networks, but not exclusively, to a computer-implementedmethod for contextual generation of an ephemeral network of trustednetwork nodes and recipients. The present disclosure relates further toa related system for establishing ephemeral networks, and a computerprogram product for operating such a system.

Many vehicle manufacturers provide vehicle infotainment systems, whichpresent information and provide for interaction with and connectivity tomobile computing devices and other network resources. From self-drivingcars that map out routes, to vehicles with WIFI that log network access,to GPS enabled infotainment and navigation systems noting locations ofwork and home, vehicle data sharing may present data security risks tousers, drivers, and passengers alike. The amount and type of dataaccessed by, shared with, or transmitted through vehicles represents adigital fingerprint or profile of users, drivers, and passengers. Thisdigital fingerprint or profile may be accessed for data theft orinappropriate usage by third parties who gain physical or logical accessto the vehicle and its associated data processing or data retentionresources. Such data security risks arise where vehicles, and their dataprocessing, storage, and communication resources, are used by multipleusers.

For example, a user may temporarily engage in information exchanges witha rental car or a ride sharing vehicle. Users may intentionally orinadvertently upload contact information, song preferences, callhistory, GPS location details, browsing history or preferences, or anyother profile or usage information from a mobile computing device to thevehicle infotainment system or WIFI enabled resources. The data may bepersistent in the vehicle's memory and, in some cases, may be sharedindiscriminately with others who drive, service, or otherwise access thevehicle. A user's personal data, shared inadvertently or intentionally,may remain on the vehicle with no time or access constraints, unless thedata is explicitly removed from the vehicle. Most users fail toexplicitly remove their data from temporarily used vehicles. Further,this data persistence may raise issue with some regulatory bodies andlaws (e.g., the General Data Protection Regulation (GDPR)) that seek tomanage data privacy and data protections.

Embodiments of the present disclosure provide methods, systems, andcomputer program products for establishing ephemeral networks. Thepresent disclosure enables generation of ephemeral networks of trustednetwork nodes and recipients. For example, embodiments described in thepresent disclosure may dynamically provide a mechanism to enable atrusted community of communication partners as recipients for automotiveand personal data to access information on an ephemeral, conditional, ortime-based basis. Embodiments of the present disclosure deploy atrusted, timed connection for establishing networks and sharing personalor contextual information for a user (e.g., user profile, user profileinformation, or user personal information). The networks and datasharing protections provided by the present disclosure enable sharing ofinformation between authorized parties and trusted sources of interestbased on analysis of a contextual situation.

Embodiments of the present disclosure deploy dynamic blockchainprotocols to form a network of authoritative parties for personal orsensitive data sharing. These networks may be ephemeral or sharablebased on usage context of the vehicle. Profile/nodal information maystay in the shared network once the context of use (e.g., a vehicle rideor a rental agreement) is terminated. The blockchain network may retainthe node. However, data from the vehicle or shared during a network'sestablished duration will be removed based on the ingested or determinedparameters for the context of use. Thus, embodiments of the presentdisclosure may provide a singular method, system, or computer programproduct to share data discriminately and eradicate the data in a timelyand measured manner to prohibit valuable information from being accessedby unintended users. Further, embodiments of the present disclosureenable application of time-based restraints upon the data itself.

Some embodiments of the concepts described herein may take the form of asystem or a computer program product. For example, a computer programproduct may store program instructions that, when executed by one ormore processors of a computing system, cause the computing system toperform operations described above with respect to the computerimplemented method. By way of further example, the system may comprisecomponents, such as processors and computer readable storage media. Thecomputer readable storage media may interact with other components ofthe system to cause the system to execute program instructionscomprising operations of the computer implemented method, describedherein. For the purpose of this description, a computer-usable orcomputer-readable medium may be any apparatus that may contain means forstoring, communicating, propagating, or transporting the program foruse, by, or in connection with, the instruction execution system,apparatus, or device.

Referring now to FIG. 1 , a block diagram of an example computingenvironment 100 is shown. The present disclosure may be implementedwithin the example computing environment 100. In some embodiments, thecomputing environment 100 may be included within or embodied by acomputer system, described below. The computing environment 100 mayinclude an ephemeral network system 102. The ephemeral network system102 may comprise an event component 110, a member component 120, anetwork component 130, and a deletion component 140. The event component110 detects events initiating or terminating establishment of ephemeralnetworks. The event component 110 may also detect or determine eventconditions related to initiating, terminating, or exclusion events. Themember component 120 determines network members eligible for access toephemeral networks. The network component 130 establishes and terminatesephemeral networks. The deletion component 140 deletes data transmittedover or accessible to the ephemeral network upon termination of theephemeral network. Although described with distinct components, itshould be understood that, in at least some embodiments, components maybe combined or divided, or additional components may be added, withoutdeparting from the scope of the present disclosure.

Referring now to FIG. 2 , a flow diagram of a computer-implementedmethod 200 is shown. The computer-implemented method 200 is a method forcontextual generation of an ephemeral network. In some embodiments, thecomputer-implemented method 200 may be performed by one or morecomponents of the computing environment 100, as described in more detailbelow.

At operation 210, the event component 110 detects an initiating eventfor network generation. In some embodiments, the initiating event isassociated with a user of a first computing device. The initiating eventmay be detected proximate to a time of network generation. In someembodiments, the initiating event is detected at a time prior to networkgeneration, indicating a later time at which a network is to begenerated. Initiating events may be events associated with vehicles suchas renting a vehicle, scheduling a rideshare, receiving a loaned vehiclefrom a vehicle repair establishment, or any other suitable vehiclerelated event. The event component 110 may detect the initiating eventbased on direct action of a user, indirect action of a user, orcontextual input to the first computing device. For example, aninitiating event may be detected by the event component 110 identifyinginitiation of a vehicle rental agreement, a vehicle purchase, or arideshare confirmation.

Detection of the initiating event may be performed using one or moresub-operations. In some embodiments, the event component 110 detects theinitiating event by identifying a candidate event from contextual inputfor the first computing device. The candidate event may represent avehicular activity associated with a specified time (e.g., a startingtime). In some embodiments, the event component detects the initiatingevent through situational or contextual information. Situational orcontextual information may be gathered through phone or messaginghistory, social media interaction, calendar entries, microphone, camera,or application integrations.

For example, the event component 110 may detect the initiating eventthrough Mel Frequency Cepstral Coefficient (MFCC) speech patternanalysis and context extraction using Latent Dirichlet Allocation (LDA)and Natural Language Processing (NLP) infusion to identify, detect, orretrieve speech relating to the initiating event from a phone call, amessage, or an email. Similarly, the event component 110 may detect theinitiating event through NLP clustering of social media interaction,based on intensity and volume of engagement indicating the initiatingevent. The event component 110 may detect the initiating event using amicrophone of the first computing device using conversational contextand immediate communication partners as candidates for communicationsharing. The event component 110 may detect the initiating event usingthe camera by identifying individuals within a vicinity of an ephemeralcontext which are candidates for information sharing for a durationspecified in a given context of a current situation characterized by alocation, activity, and time. Application specific integrations mayrepresent partner applications passing initiating event data to theevent component 110. For example, a rental car application may pass anindication of a car rental reservation to the event component 110.

In some instances, a bag of words algorithm, and associated topicmodeling, is deployed within the event component 110 to generate ordetermine context based on associative context. Some embodiments of thebag of words algorithm may be understood as shown below in pseudocode.

-   -   dataset=pd.read_data([doc_text_phone/SMS], [Social media        information], [calendar entry], [R-CNN enabled camera context,        time])

Creating a bag of words model:

-   -   from sklearn.feature_extraction.text import CounterVectorizer    -   cv=CountVectorizer(max_features=n) #n=feature set    -   X=cv.fit_transform(corpus).toarray( )    -   Y=dataset.iloc[;5].values #time duration estimation based on        initial set of inputs

As discussed above, a context or ephemeral situation may be identifiedbased on input to the first computing device. In some embodiments, theevent component 110 detects the initiating event based on activity. Theevent component 110 may detect location, activity (e.g., input, physicalaction, or logical action) of the first computing device, time,proximity to vehicle, combinations thereof, and other suitableinformation to determine an activity of a user and detect the initiatingevent or a candidate initiating event. For example, where a user hasrented a car from a rental service, the activity or input related torenting the car may represent the initiating event. A user entering arideshare agreement, a rideshare vehicle, or a rideshare service networkmay be determined as activities or input representing the initiatingevent.

In some embodiments, the event component 110 determines one or more datasharing attributes for the candidate event. The event component 110 maydetermine data sharing attributes based on activity, input, or context,as described above. In some embodiments, data sharing attributes includeprivacy permissions for data sharing, network type (e.g., closed networkbetween specified devices or a network capable of enabling connection tothird party network resources), authorized device types, networkproximity, candidate members, combinations thereof, and any otherattributes or characteristics effecting data to be shared across thenetwork. In some embodiments, data sharing attributes includepermissions for access of songs, access of SMS messages, access ofbraking system (e.g., monitoring actions of the braking system), accessof steering system (e.g., monitoring actions of the steering system),cooling/heating, environmental preferences, streaming video/musicactivities, contact information, calendar entries, agenda information,map locations, routing information, marked locations, combinationsthereof, and any permissions for sharing any other suitable informationcapable of being transmitted by one or more of the vehicle and thecomputing devices associated with network members.

At operation 220, the event component 110 determines a duration of theinitiating event. The event component 110 may determine the duration ofthe initiating event from the input, activities, context, or other dataused to determine the duration of the initiating event. In someembodiments, the event component 110 determines the duration of theinitiating even directly from data describing the initiating event. Forexample, where the initiating event is detected through establishment orconfirmation of a rental agreement, the event component 110 maydetermine the duration of the initiating event as a time extendingbetween a scheduled pick up of the rental vehicle and a scheduled dropoff of the rental vehicle. In some embodiments, the event component 110determines the duration of the initiating event by estimating anexpected time for the initiating event. For example, where theinitiating event is detected through a rideshare confirmation orentering a rideshare vehicle, the event component 110 may determine apredicted trip time for the rideshare. The predicted trip time may becalculated or extracted based on a distance between a starting andending location, ambient traffic conditions, routing information,combinations thereof, or any other suitable information accessible tothe event component 110.

At operation 230, the member component 120 determines a set of networkmembers. The set of network members are associated with a set ofcomputing devices. In some embodiments, the set of network members isdetermined based on the initiating event and the duration. The set ofnetwork members may be determined from one or more parties of acommunication indicating the initiating event. For example, where theinitiating event is detected from a car rental transaction, the user anda rental car administrator may be candidate members for inclusion in theset of network members. In some embodiments, the set of network membersare determined based on proximity to the first computing device of theuser. For example, where the initiating event is entry into a ridesharevehicle, candidate members or network members may be determined as usersor mobile computing devices within a predetermined or dynamicallydetermined proximity to the first computing device. The set of networkmembers may also be determined based on user data within the firstcomputing device. In some instances, network members are determinedbased on a contact list of the user on the first computing device,recent communications (e.g., phone calls or SMS messages) stored on thefirst computing device, combinations thereof, or any other suitableinformation contained on the first computing device. In someembodiments, combinations of differing data may be used to determine theset of network members. For example, network members may be determinedas users or computing devices with which the first computing device hasrecently communicated, and which are within a close proximity to thefirst computing device. By way of further example, co-riders in a rideshare with whom the first computing device has recently sent or receiveda message may be determined to be network members.

In some embodiments, the member component 120 determines sharingpermissions for the set of network members. Each member of the set ofnetwork members may have differing sharing permissions. Sharingpermissions may be based on a role or position within the network, arelation to the user or the first computing device for which the networkwill be generated, or on any suitable attribute or characteristic ofeach network member. For example, where a rental car administrator isdetermined as a network member, the rental car administrator may beprovided a passive sharing permission. Passive sharing permissions mayindicate a network member may be precluded from transmitting informationor accessing certain personal information shared on the network. Forexample, the rental car administrator may have a sharing permission inwhich only data relating to vehicle safety or vehicle damage istransmitted to the rental car administrator. Sharing permissions mayalso include active sharing permissions in which a network member maytransfer or receive data from other network members. Although activesharing permissions may enable additional interaction between users, insome embodiments, network members with active sharing permissions maystill be precluded from accessing personal or identifying information ofthe user.

The set of network members may be determined using one or moresub-operations. In some embodiments, the member component 120 determinesthe set of network members by identifying one or more sets of entitiesor candidate entities for the network. The member component 120 mayidentify a first set of entities associated with the initiating event.The first set of entities may be parties to a communication representingthe initiating event. The first set of entities may include interestedparties for the initiating event, such as a representative or qualitycontrol agent of a rental car agency or ride share company or aninsurance agent. The member component 120 may detect a second set ofentities proximate to the first computing device. The second set ofentities may be individuals or computing devices positioned within alocation determined to be close to the first computing device. Proximitybetween two computing devices may indicate common purpose, activity, orrelationship suitable for inclusion in the network members. The membercomponent 120 may determine a third set of entities based on one or morecontextual inputs for the first computing device. The third set ofentities may include individuals or computing devices with which thefirst computing device has recently communicated or with which the firstcomputing device has communicated regarding the initiating event.Although described with a specified number of sets of entities and withspecified relationships or roles, it should be understood that themember component 120 may determine any number of sets of entities ascandidate entities and such candidate entities may have any suitablerelationship with the user or the first computing device.

In some embodiments, the member component 120 determines the set ofnetwork members by selecting the set of network members from one or moreof the first set of entities, the second set of entities, and the thirdset of entities. The member component 120 may prune sets of entities orindividuals from a given set of entities to determine the set of networkmembers. For example, the member component 120 may remove entities fromthe set of network members who have not communicated with the firstcomputing device or are not located within a suitable proximity of thefirst computing device. The member component 120 may determine the setof network members by building a list of entities based on importance,relevance, or matching attributes of the initiating event. In someembodiments, the member component 120 determines the set of networkmembers by building or pruning a list of candidate entities from thefirst, second, and third set of entities and generating a user interfacescreen including a representation for each candidate entity. The membercomponent 120 may present the user interface screen at the firstcomputing device and include candidate entities in the set of networkmembers which have been selected by the user of the first computingdevice.

At operation 240, the network component 130 establishes an ephemeralnetwork. In some embodiments, the ephemeral network connects computingdevices associated with the set of network members. The ephemeralnetwork may be a dynamic blockchain-based consensus network. The networkcomponent 130 may establish the ephemeral network as an ad hoc networkwith temporal restrictions, between at least a portion of the set ofnetwork members, based on the duration of the initiating event. Onceestablished, data passed through the ephemeral network is tagged andapplied to a ledger of the blockchain accordingly. Members of theestablished ephemeral network may be granted access to chained eventsand authorized data transferred within the ephemeral network. In someembodiments, members of the ephemeral network are granted access andauthoritative access capability within the temporal restrictions (e.g.,the duration of the initiating event) of the ephemeral network andwithin established parameters. Once established, network membersconnected to the ephemeral network may be authorized to accessinformation associated with sharing attributes and permissions,described above with respect to operation 210.

In some embodiments, establishing the ephemeral network may beperformed, at least in part, as shown below in pseudocode.

#RiftConsensusAlgorithm for network establishment b/w users and sharingsensors information/profile preferences  “”Read all sensory/profile dataand save data in memory for latter usage.””  required_params = (Userdata= BagofWords(Dataset[1.5], Ridesharers_data)  default_params ={‘sensorReadingsKey’: ‘sensorReadings’}  def run(self): #running user'ssensory values in the vehicle and retaining for future  referencing  for node in self.ReadUser_Network.nodes():   node.memory.update({self.sensorReadingsKey:   node.compositeSensor.read()})

The network component 130 may establish the ephemeral network based onan occurrence of the initiating event, an action associated with theinitiating event, or other suitable trigger. Triggers for eachinitiating event may be defined by one or more of the initiating eventand the duration of the initiating event. In some embodiments, thenetwork component 130 establishes the ephemeral network by determining acurrent time matches an event time for the initiating event. In suchinstances, the initiating event may be associated with an event timebeginning the initiating event. The network component 130 may detect avehicle is proximate to the first computing device. The vehicle may beassociated with the initiating event.

In some embodiments, when establishing the ephemeral network, thenetwork component 130 generates one or more user interface elements orscreens to establish the ephemeral network as a consensus network. Theephemeral consensus network allows network members to opt in or opt outprior to inclusion in or establishment of the ephemeral network. In someembodiments, the network component generates a network permissioninterface at a first computing device of a user associated with aninitiating event. The network component 130 may generate the networkpermission interface based on determining that a current time matches anevent time for the initiating event. The network component 130 maygenerate the network permission interface based on detecting a vehicleis proximate to the first computing device, where the vehicle isassociated with the initiating event. The network permission interfacemay include a plurality of interface elements. The interface elementsmay represent a plurality of options including acceptance of access tothe ephemeral network, sharing options (e.g., opt in or opt outpermissions indicating subject matter the user consents to share),network members for inclusion in the ephemeral network, combinationsthereof, or any other suitable network permissions. Upon receivingselection of a user interface element indicating acceptance of a networkconnection, the network component 130 connects the first computingdevice to the ephemeral network. In some embodiments, connecting thefirst computing device to the ephemeral network grants access betweenthe first computing device and one or more communication elements of thevehicle, such as a vehicle WIFI hot spot or the vehicle infotainmentsystem.

The network component 130 may also generate a network permissioninterface at a set of computing devices associated with the set ofnetwork members. The network component 130 may generate the networkpermission interface for each computing device in a manner similar to orthe same as described above. The network component 130 may present thenetwork permission interface at each computing device of the set ofcomputing devices. Upon receiving permission responses from one or morecomputing devices of the set of computing devices, the network component130 connects the one or more computing devices to the ephemeral network.In some instances, a set of candidate network members may self-select tofurther reduce the set of network members allowed to share data acrossthe ephemeral network.

At operation 250, the network component 130 terminates the ephemeralnetwork. In some embodiments, termination of the ephemeral network isperformed in response to detecting a completion event. Upon completionor termination of the ephemeral network, or ending of the temporalallowance for the ephemeral network, all access to the set of networkmembers is revoked. Further access to the ephemeral network is deniedand restricted according to an agreement established within theblockchain authorization.

In some embodiments, the network component 130 cooperates with one ormore other components of the ephemeral network system 102 to determinecompletion events. The network component 130 may determine a completionevent by identifying one or more of a termination time, a terminationactivity, or a termination condition. Completion events may includetermination dates, ending trip times, trip destinations, combinationsthereof, and any other suitable event which ends the initiating event.In some instances, the network component 130 identifies a terminationtime for the initiating event. In such instances, the termination timeis based on the duration of the initiating event and an establishingtime for the ephemeral network. The network component 130 may thendetermine a current time matches the termination time for the initiatingevent. Upon identifying a match between the current time and thetermination time, the network component 130 terminates the ephemeralnetwork. In some instances, the network component 130 determines thecompletion event as arrival at a destination. The network component 130may access location data for at least one computing device accessing theephemeral network, and match a current location of the computing devicewith a destination for a trip associated with the initiating event. Uponidentifying a match between a current location and the destination, thenetwork component 130 terminates the ephemeral network.

For example, once a ridesharing service or car rental service is over,based on computation from one or more component of the ephemeral networksystem 102, the network component 130 terminates the ephemeral network.In some embodiments, the network component 130 terminates the ephemeralnetwork by initiating a destruct or deletion command for blocking accessto a node associated with the ephemeral network within the blockchain.In some instances, the destruction or deletion command initiates removalof profile information, described below, from the public ledger.

At operation 260, the deletion component 140 removes member informationfor the set of network members. In some embodiments, removal of themember information is performed in response to terminating the ephemeralnetwork. The deletion component 140 may remove member information bydeleting personal profile information from a public ledger, which is notblockchain based. Removal of the member information deletes personal,private, or sensitive information from the vehicle and returns one ormore settings of the infotainment system in the vehicle to a defaultmode. Node information associated with the ephemeral network may betransmitted to the network component 130 and a private blockchainnetwork. The private blockchain network may only share the nodeinformation with authorized or concerned parties of interest.

In some embodiments, the deletion component 140 cooperates with thenetwork component 130 to remove member information. The deletioncomponent 140 may receive a termination indication from the networkcomponent 130. The termination indication may represent termination ordeconstruction of the ephemeral network by the network component 130.The deletion component 140 may then initiate a deletion command toremove profile information from a public ledger. In some embodiments,once the deletion component 140 deletes, scrubs, overwrites, orotherwise removes the member information, the deletion component 140 maycooperate with the network component 130 to transmit node information toa blockchain network associated with at least one network member of theset of network members. Network members having access to the nodeinformation may be administrators of the ephemeral network system 102,insurance administrators, rental car administrators, rideshareadministrators, or other entities or network members having suitablepermissions or authorization to access anonymized, depersonalized, orother retained information relating to the blockchain retained aspectsof the node information.

FIG. 3 shows a flow diagram of an embodiment of a computer-implementedmethod 300 for contextual generation of an ephemeral network. The method300 may be performed by or within the computing environment 100. In someembodiments, the method 300 comprises or incorporates one or moreoperations of the method 200. In some instances, operations of themethod 300 may be incorporated as part of or sub-operations of themethod 200.

In operation 310, the event component 110 identifies an exclusion event.The exclusion event may be identified during a duration of an initiatingevent. Exclusion events may be events which interrupt the initiatingevent, the duration of the initiating event, or the completion event. Insome instances, an exclusion event may be an airbag deployment, a crash,a prolonged stop, or other indicators of early termination of anexpected activity associated with the initiating event. For example, ifa vehicle is involved in a collision and an airbag is deployed, anexclusion event is triggered.

In operation 320, the event component 110 identifies exclusion eventdata representing input to one or more of a first computing device and aset of computing devices. The exclusion event data may be associatedwith the exclusion event. Exclusion event data may include authorizedcausational data. For example, information related to braking, speedbefore airbag deployment, steering actions, infotainment presentations,computing device presentations, combinations thereof, or other suitableinformation relating to the exclusion event. The exclusion event datamay be captured for a time immediately preceding the exclusion event.For example, exclusion event data may be captured and retained for five,ten, fifteen, or thirty seconds prior to the exclusion event. In someinstances, a time for which exclusion event data is captured andretained may be controlled by a vehicle black box, the infotainmentsystem, insurance agreements, or combinations thereof.

In operation 330, the network component 130 determines one or morenetwork sharing permissions for the ephemeral network. The sharingpermissions may indicate exclusion event data capable of being retainedbased on one or more agreements, user preferences, network memberpreferences, or other suitable constraints. Network sharing permissionsmay be set automatically or may be set manually. In some embodiments, arental or rideshare agreement may indicate an amount of time and typesof data to be retained by the event component 110 in the event of anexclusion event. The network component 130 may access the agreement anddetermine associated network sharing permissions. The network component130 may also determine the network sharing permissions by accessing thepermissions on a computing device, a network node, or any other suitablestorage location.

In operation 340, the network component 130 transmits at least a portionof the exclusion event data to a network member of the set of networkmembers associated with the ephemeral network. In some embodiments, theportion of exclusion event data is transmitted based on the one or morenetwork sharing permissions. The network component 130, based on sharingchoices or sharing permissions, may share exclusion event data with aresponsible network member such as an insurance entity, a ridesharecompany, a rental car company, or other suitably responsible networkmembers. In some instances, exclusion event data associated withtemporal choices made at a time of the exclusion event may be shared,precluding data captured prior to or after the exclusion event.

In some instances, network sharing permissions may be overridden. Wherenetwork sharing permissions exclude sharing information relating todriving actions, an exclusion event indicating early termination of avehicle trip due to accident or erratic actions may cause the networkcomponent 130 and the event component 110 to override the networksharing permissions. In such instances, the exclusion event data whichis associated with an override condition (e.g., indications of dangerousactivities or accident) may be retained and transmitted the networkmember.

Embodiments of the present disclosure enable secured interactions withvarying networked devices in a time-limited manner, removing private orsensitive data once access to the network is terminated. For example, acouple engaging in driving and sharing one or more profiles with avehicle infotainment system. Initially, a first user profile is sharedwith a second user profile, inclusive of song collections, messages, andother information. The information may be inherently shared with otherusers within the context of the trip. Once the travel experience hasended, the shared information between the first user and the second usercan be deleted, continued, or archived according to user preferences. Byway of further example, embodiments of the present disclosure enable afirst user, entering a rideshare vehicle with other individuals withwhom the first user would like to share data for the duration of theride, to establish a temporary network and share certain information.During the course of the time-established ride, sharing may be performedby the first user and other users within the rideshare vehicle. Upon anestablished termination of the rideshare time, all sharing andcommunication between shared users is terminated and deleted. Theblockchain may be used as a mechanism to acknowledge that previouslyestablished users are no longer granted access to privileged informationbased on time constraints. Embodiments of the present disclosure mayenable a user to establish a long-term relationship with an establishednetwork of participants to access vehicular and cellular data within aparticular vehicle. After a life of the vehicle has expired (e.g.,transfer of ownership, destruction, etc.), all data associated with thevehicle is expunged from participant records.

Embodiments of the present disclosure may be implemented together withvirtually any type of computer, regardless of the platform beingsuitable for storing and/or executing program code. FIG. 4 shows, as anexample, a computing system 400 (e.g., cloud computing system) suitablefor executing program code related to the methods disclosed herein andfor contextual generation of an ephemeral network.

The computing system 400 is only one example of a suitable computersystem and is not intended to suggest any limitation as to the scope ofuse or functionality of embodiments of the present disclosure describedherein, regardless, whether the computer system 400 is capable of beingimplemented and/or performing any of the functionality set forthhereinabove. In the computer system 400, there are components, which areoperational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 400 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like. Computersystem/server 400 may be described in the general context of computersystem-executable instructions, such as program modules, being executedby a computer system 400. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 400 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both, local and remote computer system storage media, includingmemory storage devices.

As shown in the figure, computer system/server 400 is shown in the formof a general-purpose computing device. The components of computersystem/server 400 may include, but are not limited to, one or moreprocessors 402 (e.g., processing units), a system memory 404 (e.g., acomputer-readable storage medium coupled to the one or more processors),and a bus 406 that couple various system components including systemmemory 404 to the processor 402. Bus 406 represents one or more of anyof several types of bus structures, including a memory bus or memorycontroller, a peripheral bus, an accelerated graphics port, and aprocessor or local bus using any of a variety of bus architectures. Byway of example, and not limiting, such architectures include IndustryStandard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus,Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA)local bus, and Peripheral Component Interconnects (PCI) bus. Computersystem/server 400 typically includes a variety of computer systemreadable media. Such media may be any available media that is accessibleby computer system/server 400, and it includes both, volatile andnon-volatile media, removable and non-removable media.

The system memory 404 may include computer system readable media in theform of volatile memory, such as random-access memory (RAM) 408 and/orcache memory 410. Computer system/server 400 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, a storage system 412 may be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a ‘hard drive’). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a ‘floppy disk’), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media may be provided.In such instances, each can be connected to bus 406 by one or more datamedia interfaces. As will be further depicted and described below, thesystem memory 404 may include at least one program product having a set(e.g., at least one) of program modules that are configured to carry outthe functions of embodiments of the present disclosure.

The program/utility, having a set (at least one) of program modules 416,may be stored in the system memory 404 by way of example, and notlimiting, as well as an operating system, one or more applicationprograms, other program modules, and program data. Program modules mayinclude one or more of the event component 110, the member component120, the network component 130, and the deletion component 140, whichare illustrated in FIG. 1 . Each of the operating systems, one or moreapplication programs, other program modules, and program data or somecombination thereof, may include an implementation of a networkingenvironment. Program modules 416 generally carry out the functionsand/or methodologies of embodiments of the present disclosure, asdescribed herein.

The computer system/server 400 may also communicate with one or moreexternal devices 418 such as a keyboard, a pointing device, a display420, etc.; one or more devices that enable a user to interact withcomputer system/server 400; and/or any devices (e.g., network card,modem, etc.) that enable computer system/server 400 to communicate withone or more other computing devices. Such communication can occur viaInput/Output (I/O) interfaces 414. Still yet, computer system/server 400may communicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 422. As depicted, network adapter 422may communicate with the other components of computer system/server 400via bus 406. It should be understood that, although not shown, otherhardware and/or software components could be used in conjunction withcomputer system/server 400. Examples include, but are not limited to:microcode, device drivers, redundant processing units, external diskdrive arrays, RAID systems, tape drives, and data archival storagesystems, etc.

It is to be understood that although this disclosure includes a detaileddescription on cloud computing, implementation of the teachings recitedherein are not limited to a cloud computing environment. Rather,embodiments of the present disclosure are capable of being implementedin conjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Service models may include software as a service (SaaS), platform as aservice (PaaS), and infrastructure as a service (IaaS). In SaaS, thecapability provided to the consumer is to use the provider'sapplications running on a cloud infrastructure. The applications areaccessible from various client devices through a thin client interfacesuch as a web browser (e.g., web-based email). The consumer does notmanage or control the underlying cloud infrastructure including network,servers, operating systems, storage, or even individual applicationcapabilities, with the possible exception of limited user-specificapplication configuration settings. In PaaS, the capability provided tothe consumer is to deploy onto the cloud infrastructure consumer-createdor acquired applications created using programming languages and toolssupported by the provider. The consumer does not manage or control theunderlying cloud infrastructure including networks, servers, operatingsystems, or storage, but has control over the deployed applications andpossibly application hosting environment configurations. In IaaS, thecapability provided to the consumer is to provision processing, storage,networks, and other fundamental computing resources where the consumeris able to deploy and run arbitrary software, which can includeoperating systems and applications. The consumer does not manage orcontrol the underlying cloud infrastructure but has control overoperating systems, storage, deployed applications, and possibly limitedcontrol of select networking components (e.g., host firewalls).

Deployment models may include private cloud, community cloud, publiccloud, and hybrid cloud. In private cloud, the cloud infrastructure isoperated solely for an organization. It may be managed by theorganization or a third party and may exist on-premises or off-premises.In community cloud, the cloud infrastructure is shared by severalorganizations and supports specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partythat may exist on-premises or off-premises. In public cloud, the cloudinfrastructure is made available to the general public or a largeindustry group and is owned by an organization selling cloud services.In hybrid cloud, the cloud infrastructure is a composition of two ormore clouds (private, community, or public) that remain unique entitiesbut are bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure that includes anetwork of interconnected nodes.

Referring now to FIG. 5 , illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 includes one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 5 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 6 , a set of functional abstraction layersprovided by cloud computing environment 50 (FIG. 5 ) is shown. It shouldbe understood in advance that the components, layers, and functionsshown in FIG. 5 are intended to be illustrative only and embodiments ofthe disclosure are not limited thereto. As depicted, the followinglayers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture-based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may include applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and network traffic direction processing 96.

Cloud models may include characteristics including on-demandself-service, broad network access, resource pooling, rapid elasticity,and measured service. In on-demand self-service a cloud consumer mayunilaterally provision computing capabilities such as server time andnetwork storage, as needed automatically without requiring humaninteraction with the service's provider. In broad network access,capabilities are available over a network and accessed through standardmechanisms that promote use by heterogeneous thin or thick clientplatforms (e.g., mobile phones, laptops, and PDAs). In resource pooling,the provider's computing resources are pooled to serve multipleconsumers using a multi-tenant model, with different physical andvirtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter). In rapidelasticity, capabilities can be rapidly and elastically provisioned, insome cases automatically, to quickly scale out and rapidly released toquickly scale in. To the consumer, the capabilities available forprovisioning often appear to be unlimited and can be purchased in anyquantity at any time. In measured service, cloud systems automaticallycontrol and optimize resource use by leveraging a metering capability atsome level of abstraction appropriate to the type of service (e.g.,storage, processing, bandwidth, and active user accounts). Resourceusage can be monitored, controlled, and reported, providing transparencyfor both the provider and consumer of the utilized service.

The descriptions of the various embodiments of the present disclosurehave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinaryskills in the art without departing from the scope and spirit of thedescribed embodiments. The terminology used herein was chosen to bestexplain the principles of the embodiments, the practical application ortechnical improvement over technologies found in the marketplace, or toenable others of ordinary skills in the art to understand theembodiments disclosed herein.

The present invention may be embodied as a system, a method, and/or acomputer program product. The computer program product may include acomputer-readable storage medium (or media) having computer readableprogram instructions thereon for causing a processor to carry outaspects of the present invention.

The computer-readable storage medium may be an electronic, magnetic,optical, electromagnetic, infrared or a semi-conductor system for apropagation medium. Examples of a computer-readable medium may include asemi-conductor or solid state memory, magnetic tape, a removablecomputer diskette, a random access memory (RAM), a read-only memory(ROM), a rigid magnetic disk and an optical disk. Current examples ofoptical disks include compact disk-read only memory (CD-ROM), compactdisk-read/write (CD-R/W), DVD and Blu-Ray-Disk.

The computer-readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer-readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer-readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disk read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer-readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from acomputer-readable storage medium or to an external computer or externalstorage device via a network, for example, the Internet, a local areanetwork, a wide area network and/or a wireless network. The network maycomprise copper transmission cables, optical transmission fibers,wireless transmission, routers, firewalls, switches, gateway computersand/or edge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer-readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including anobject-oriented programming language such as Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general-purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatuses, or anotherdevice to cause a series of operational steps to be performed on thecomputer, other programmable apparatus or other device to produce acomputer implemented process, such that the instructions which executeon the computer, other programmable apparatuses, or another deviceimplement the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowcharts and/or block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or act or carry out combinations of special purpose hardwareand computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to limit the present disclosure. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will further be understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or steps plus function elements in the claims below are intendedto include any structure, material, or act for performing the functionin combination with other claimed elements, as specifically claimed. Thedescription of the present disclosure has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the present disclosure in the form disclosed. Manymodifications and variations will be apparent to those of ordinaryskills in the art without departing from the scope of the presentdisclosure. The embodiments are chosen and described in order to explainthe principles of the present disclosure and the practical application,and to enable others of ordinary skills in the art to understand thepresent disclosure for various embodiments with various modifications,as are suited to the particular use contemplated.

The descriptions of the various embodiments of the present disclosurehave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A computer-implemented method, comprising:determining a set of network members associated with a set of computingdevices; establishing an ephemeral network connecting at least a portionof the computing devices associated with the set of network members;terminating the ephemeral network in response to detecting a completionevent; and removing member information from the portion of the computingdevices associated with the set of network members in response toterminating the ephemeral network.
 2. The method of claim 1, wherein themethod further comprises: detecting an initiating event for theephemeral network, the initiating event associated with at least onecomputing device of the set of computing devices.
 3. The method of claim2, wherein the method further comprises: determining one or more datasharing attributes for the initiating event.
 4. The method of claim 3,wherein the one or more data sharing attributes are determined based onone or more characteristics associated with the initiating event.
 5. Themethod of claim 4, wherein the one or more characteristics include oneor more of an activity type, an input type, and a context of theinitiating event.
 6. The method of claim 3, wherein the one or more datasharing attributes include one or more of a privacy permission for datasharing over the ephemeral network, a network type for the ephemeralnetwork, and a network proximity for the ephemeral network.
 7. Themethod of claim 3, wherein the one or more data sharing attributesinclude one or more of a set of authorized device types for computingdevices communicating with the ephemeral network, a set of device basedprivacy permissions associated with the set of authorized device types,a set of candidate members for inclusion in the ephemeral network, and aset of role based privacy permissions associated with the set ofcandidate members.
 8. A system, comprising: one or more processors; anda computer-readable storage medium, coupled to the one or moreprocessors, storing program instructions that, when executed by the oneor more processors, cause the one or more processors to performoperations comprising: determining a set of network members associatedwith a set of computing devices; establishing an ephemeral networkconnecting at least a portion of the computing devices associated withthe set of network members; terminating the ephemeral network inresponse to detecting a completion event; and removing memberinformation from the portion of the computing devices associated withthe set of network members in response to terminating the ephemeralnetwork.
 9. The system of claim 8, wherein the operations furthercomprise: detecting an initiating event for the ephemeral network, theinitiating event associated with at least one computing device of theset of computing devices.
 10. The system of claim 9, wherein theoperations further comprise: determining one or more data sharingattributes for the initiating event.
 11. The system of claim 10, whereinthe one or more data sharing attributes are determined based on one ormore characteristics associated with the initiating event.
 12. Thesystem of claim 11, wherein the one or more characteristics include oneor more of an activity type, an input type, and a context of theinitiating event.
 13. The system of claim 10, wherein the one or moredata sharing attributes include one or more of a privacy permission fordata sharing over the ephemeral network, a network type for theephemeral network, and a network proximity for the ephemeral network.14. The system of claim 10, wherein the one or more data sharingattributes include one or more of a set of authorized device types forcomputing devices communicating with the ephemeral network, a set ofdevice based privacy permissions associated with the set of authorizeddevice types, a set of candidate members for inclusion in the ephemeralnetwork, and a set of role based privacy permissions associated with theset of candidate members.
 15. A computer program product comprising acomputer readable storage medium having program instructions embodiedtherewith, the program instructions being executable by one or moreprocessors to cause the one or more processors to perform operationscomprising: determining a set of network members associated with a setof computing devices; establishing an ephemeral network connecting atleast a portion of the computing devices associated with the set ofnetwork members; terminating the ephemeral network in response todetecting a completion event; and removing member information from theportion of the computing devices associated with the set of networkmembers in response to terminating the ephemeral network.
 16. Thecomputer program product of claim 15, wherein the operations furthercomprise: detecting an initiating event for the ephemeral network, theinitiating event associated with at least one computing device of theset of computing devices.
 17. The computer program product of claim 16,wherein the operations further comprise: determining one or more datasharing attributes for the initiating event.
 18. The computer programproduct of claim 17, wherein the one or more data sharing attributes aredetermined based on one or more characteristics associated with theinitiating event.
 19. The computer program product of claim 18, whereinthe one or more characteristics include one or more of an activity type,an input type, and a context of the initiating event.
 20. The computerprogram product of claim 17, wherein the one or more data sharingattributes include one or more of a privacy permission for data sharingover the ephemeral network, a network type for the ephemeral network, anetwork proximity for the ephemeral network, one or more of a set ofauthorized device types for computing devices communicating with theephemeral network, a set of device based privacy permissions associatedwith the set of authorized device types, a set of candidate members forinclusion in the ephemeral network, and a set of role based privacypermissions associated with the set of candidate members.